[mobile] .NET 11 mobile runtime configuration updates by kotlarmilos · Pull Request #11632 · dotnet/android

kotlarmilos · 2026-06-11T14:59:06Z

Description

Remove the Mono mobile test legs from build-tools, and drop the Microsoft.NET.Workload.Mono.Toolchain manifest dependency from eng/Version.Details.xml and eng/Versions.props.

Validation pipelines (must pass): dotnet-android (devdiv pipeline 12278) PR build.

Validation pins (temporary): pinned to .NET 11 test build 11.0.100-preview.6.26310.106 (AzDO dotnet-unified-build run 2996804, BAR 318158, source dotnet/dotnet@8d5d82abe13, branch dev/update-sdk-mobile-stage2) and the public general-testing NuGet feed, so CI exercises the SDK with the Mono mobile workloads and RIDs removed.

TODO before merge: revert the global.json / Version.Details.xml / Versions.props pins and the NuGet.config feed back to the official VMR versions and the main feed.

kotlarmilos · 2026-06-12T09:58:25Z

/azp run

azure-pipelines · 2026-06-12T09:58:34Z

Azure Pipelines successfully started running 1 pipeline(s).

Copilot

Pull request overview

This PR updates the repo’s .NET 11 “mobile runtime” configuration by removing Mono mobile-related dependencies (notably the Mono toolchain workload manifest) and pruning CI/build tooling paths that were exercising Mono-based mobile workloads/runtimes, while temporarily pinning to a specific .NET 11 preview SDK/feed to validate the new configuration.

Changes:

Remove Mono toolchain workload manifest dependency/version plumbing from eng/* and xaprepare.
Remove Mono-runtime test lanes (and MAUI integration test stages) from build-tools Azure Pipelines templates.
Update restore inputs for validation (temporary): add general-testing feed and pin .NET 11 preview versions.

Show a summary per file

File	Description
NuGet.config	Adds the `general-testing` feed for temporary validation restores.
eng/Versions.props	Moves to a pinned .NET 11 preview SDK version; removes Mono toolchain manifest version properties.
eng/Version.Details.xml	Updates .NET dependency versions/SHA; removes Mono toolchain manifest dependency entry.
build-tools/xaprepare/xaprepare/xaprepare.targets	Stops generating replacements for removed Mono manifest properties.
build-tools/xaprepare/xaprepare/Steps/Step_InstallDotNetPreview.cs	Removes Mono toolchain manifest copy logic; keeps Emscripten manifest copy.
build-tools/xaprepare/xaprepare/package-download.proj	Removes Mono runtime pack downloads and Mono toolchain manifest downloads (now only Android CoreCLR runtime + Emscripten manifests).
build-tools/xaprepare/xaprepare/ConfigAndData/Configurables.cs	Removes Mono toolchain manifest package directory helpers.
build-tools/xaprepare/xaprepare/Application/Properties.Defaults.cs.in	Removes default properties for Mono manifest/version variables.
build-tools/xaprepare/xaprepare/Application/KnownProperties.cs	Removes Mono manifest/version property names.
build-tools/scripts/DotNet.targets	Removes MAUI workload install step from the helper targets.
build-tools/create-packs/ConfigureLocalWorkload.targets	Simplifies “ConfigureLocalWorkload” to only install the Android manifest (no dependency-install workaround).
build-tools/automation/yaml-templates/variables.yaml	Removes the `RunMAUITestJob` variable.
build-tools/automation/yaml-templates/stage-package-tests.yaml	Removes Mono-runtime APK instrumentation legs (Interpreter/NoAot/LLVM/etc).
build-tools/automation/azure-pipelines.yaml	Removes MAUI test stage and dependency edges from the private pipeline definition.
build-tools/automation/azure-pipelines-public.yaml	Removes MAUI test stage from the public pipeline definition.

Copilot's findings

Files reviewed: 15/15 changed files
Comments generated: 3

jonathanpeppers

Overall, I'd take a different approach to this one:

Introduce the error you have here: dotnet/sdk#54713 (just temporarily put it in this workload to test)
See how red CI is
Remove tests & iterate until green

The on-device tests you removed here looks right.

But we also have a lot of MSBuild tests that parameterize on MonoVM/CoreCLR/NativeAOT that would need to run for CoreCLR/NativeAOT only.

Then we can remove the error you have in step 1 (that can come from dotnet/sdk)

jonathanpeppers · 2026-06-12T15:25:00Z

-# MAUI Tests Stage
- stage: maui_tests
-  displayName: MAUI Tests
-  dependsOn: mac_build
-  condition: and(succeeded(), ne(variables['SkipTestStages'], 'true'))
-  jobs:


This stage tests the MAUI pipeline with our product, doesn't seem like that should be deleted?

Because it is a main <-> net11.0 build, it does break sometimes until changes land in dotnet/maui/net11.0, so that's ok if this is the case here.

Restored. Kept the MAUI Tests stage in both pipeline files. Agreed it is fine for it to break until the matching changes land in net11.0, so leaving it in place.

jonathanpeppers · 2026-06-12T15:25:56Z

-    <Dependency Name="Microsoft.NET.Sdk" Version="11.0.100-preview.5.26268.112">
+    <Dependency Name="Microsoft.NET.Sdk" Version="11.0.100-preview.6.26310.106">
      <Uri>https://github.com/dotnet/dotnet</Uri>


Why are we bumping .NET the same time?

Temporary validation pin to the .NET 11 test build so the repo can be exercised against the updated SDK. Not a permanent .NET bump.

That is what maestro is for; I wouldn't do this here.

See:

[main] Update dependencies from dotnet/dotnet #11477

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The MAUI integration stage installs the full maui workload, which pulls mobile runtime workloads that are no longer produced for .NET 11. Remove the stage from the public and internal pipelines and drop the now-unused RunMAUITestJob variable. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

…able Address review feedback: the native build and MAUI-on-local-build flow still require the Mono runtime pack downloads and workload-install targets, so restore package-download.proj, DotNet.targets, Step_InstallDotNetPreview, the xaprepare property plumbing, the maui_tests stage, and the RunMAUITestJob variable. The PR now changes only the Mono mobile instrumentation test legs in stage-package-tests.yaml plus the temporary validation pins. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Surface the unsupported Mono mobile runtime build error directly in the workload to validate that no Mono mobile build paths remain in CI. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Validation now happens through the temporary Mono mobile runtime build error in the workload, so the pinned SDK version and validation package feed are no longer needed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Gate the MonoVM runtime parametrization in the build tests so the Mono variants are ignored on .NET 11 and later, where the Mono runtime is no longer supported for Android. CoreCLR and NativeAOT variants are unaffected. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The Mono runtime is no longer supported for Android in .NET 11 and later. Remove the Mono runtime variants from the build tests: - Narrow the runtime parametrization ([Values], [TestCase], and the Enum.GetValues/TestCaseSource generators) to CoreCLR and NativeAOT. - Delete the Mono-only test methods and their now-unused TestCaseSource data generators. CoreCLR and NativeAOT coverage is unchanged. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

The Mono mobile runtime is no longer supported for Android in .NET 11, so building a project with UseMonoRuntime=true now errors with NETSDK1242. The device integration test suite still enumerated AndroidRuntime.MonoVM through [Values], Enum.GetValues, [Values(...)] and [TestCase(...)], causing those emulator legs to fail. Drop the MonoVM variants and keep CoreCLR and NativeAOT, matching the conversion already applied to Xamarin.Android.Build.Tests. Mono-only tests (AOT profiler, interpreter, LLVM, AppDomain.UnhandledException, and the MonoVM-only debugger break tests) are removed. Tests that merely pinned MonoVM now use the default CoreCLR runtime. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

LoggingPropsShouldCreateOverrideDirForRelease set debug.mono.log and asserted methods.txt in the .__override__ directory, behavior that only the Mono runtime produces. With the MonoVM pin dropped the test ran on CoreCLR, where methods.txt is never emitted, so it failed. Remove the test; CoreCLR has no equivalent output. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

kotlarmilos · 2026-06-16T12:01:00Z

/azp run

azure-pipelines · 2026-06-16T12:01:10Z

Azure Pipelines successfully started running 1 pipeline(s).

jonathanpeppers · 2026-06-16T12:59:10Z

@@ -815,60 +811,14 @@
 			}, Path.Combine (Root, builder.ProjectDirectory, "startup-logcat.log"), 60), $"Output did not contain {expectedLogcatOutput}!");
 		}

-		[Test]
-		public void SubscribeToAppDomainUnhandledException ([Values] AndroidRuntime runtime)
-		{
-			const bool isRelease = true;
-			if (IgnoreUnsupportedConfiguration (runtime, release: isRelease)) {
-				return;
-			}


I don't think we should delete this test, so it can be fixed for CoreCLR/NativeAOT.

Can it be [Values (AndroidRuntime.CoreCLR, AndroidRuntime.NativeAOT)] for now?

It seems like this should pass on CoreCLR, enabling the test here for main:

[Tests] Enable SubscribeToAppDomainUnhandledException on CoreCLR #11673

jonathanpeppers · 2026-06-16T13:04:44Z

-				Assert.Ignore ("https://github.com/dotnet/runtime/issues/88625");
-
-			var abisSanitized = supportedAbis.Replace (";", "").Replace ("-", "").Replace ("_", "");
-			var path = Path.Combine ("temp", string.Format ("BuildAotNdk AndÜmläüts_{0}_{1}_{2}", abisSanitized, enableLLVM, usesAssemblyBlobs));


I wonder if it's worth refactoring this test to run with CoreCLR release mode + NativeAOT release mode.

I bet a project named BuildAotNdk AndÜmläüts is problematic -- might not work.

jonathanpeppers · 2026-06-16T13:07:31Z

 		};

-		[Test]
-		[TestCaseSource (nameof (SettingCombinationsSource))]


I think SettingCombinationsSource can be removed

jonathanpeppers · 2026-06-16T13:09:02Z

-		// TODO: make it work on CoreCLR and NativeAOT
-		[Test]
-		[TestCaseSource(nameof (VersionCodeTestSource))]
-		public void VersionCodeTests (bool seperateApk, string abis, string versionCode, bool useLegacy, string versionCodePattern, string versionCodeProperties, bool shouldBuild, string expectedVersionCode)
-		{
-			var proj = new XamarinAndroidApplicationProject () {
-				IsRelease = true,
-				MinSdkVersion = "24",
-				SupportedOSPlatformVersion = "24.0",
-			};
-
-			// MonoVM-only test, for now (changing anything in the test data changes the codes, each case must be
-			// investigated and verified manually)
-			proj.SetRuntime (AndroidRuntime.MonoVM);
-			proj.SetProperty ("Foo", "1");
-			proj.SetProperty ("GenerateApplicationManifest", "false"); // Disable $(AndroidVersionCode) support
-			proj.SetProperty (proj.ReleaseProperties, KnownProperties.AndroidCreatePackagePerAbi, seperateApk);


I think we should keep this test -- likely the only thing that validates AndroidCreatePackagePerAbi.

We can ignore if it doesn't pass, but a TODO comment to fix would be good.

Remove the temporary _ErrorOnMonoMobileRuntime target now that CI confirms no test legs build the Mono mobile runtime. The unsupported configuration is enforced by the SDK. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Restore SubscribeToAppDomainUnhandledException for CoreCLR/NativeAOT instead of deleting it. Remove the now-unused SettingCombinationsSource in InvalidConfigTests. Restore VersionCodeTests to preserve AndroidCreatePackagePerAbi coverage, ignored with a TODO until the test data is reworked for CoreCLR/NativeAOT supported ABIs. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

kotlarmilos marked this pull request as ready for review June 12, 2026 09:58

kotlarmilos requested review from jonathanpeppers and simonrozsival as code owners June 12, 2026 09:58

Copilot AI review requested due to automatic review settings June 12, 2026 09:58

kotlarmilos self-assigned this Jun 12, 2026

Copilot started reviewing on behalf of kotlarmilos June 12, 2026 09:59 View session

Copilot AI reviewed Jun 12, 2026

View reviewed changes

Comment thread build-tools/xaprepare/xaprepare/package-download.proj

Comment thread NuGet.config

Comment thread eng/Versions.props

jonathanpeppers reviewed Jun 12, 2026

View reviewed changes

kotlarmilos and others added 5 commits June 15, 2026 18:13

Update SDK workload pipeline configuration

1ef9298

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Update .NET 11 SDK to preview 6 (build 20260610.6)

87b2454

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Use validation package feed for SDK packages

e69a75c

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

kotlarmilos force-pushed the dev/update-sdk-mobile branch from bb45bf1 to a5a8047 Compare June 15, 2026 16:16

kotlarmilos and others added 4 commits June 15, 2026 20:03

Temporarily error when building with the Mono mobile runtime

8b2d263

Surface the unsupported Mono mobile runtime build error directly in the workload to validate that no Mono mobile build paths remain in CI. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Drop validation SDK pin and feed

97993b4

Validation now happens through the temporary Mono mobile runtime build error in the workload, so the pinned SDK version and validation package feed are no longer needed. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

kotlarmilos force-pushed the dev/update-sdk-mobile branch from a16677b to d115ab9 Compare June 16, 2026 07:50

kotlarmilos and others added 2 commits June 16, 2026 11:58

jonathanpeppers reviewed Jun 16, 2026

View reviewed changes

kotlarmilos and others added 2 commits June 16, 2026 16:59

Conversation

kotlarmilos commented Jun 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Uh oh!

kotlarmilos commented Jun 12, 2026

Uh oh!

azure-pipelines Bot commented Jun 12, 2026

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Copilot's findings

Uh oh!

Uh oh!

Uh oh!

Uh oh!

jonathanpeppers left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

kotlarmilos commented Jun 16, 2026

Uh oh!

azure-pipelines Bot commented Jun 16, 2026

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

3 participants

kotlarmilos commented Jun 11, 2026 •

edited

Loading

jonathanpeppers left a comment •

edited

Loading